feat(landing): Astro 5 landing page with EN/FR i18n#12
Merged
Conversation
- Add landing/ as an independent Astro 5 + Tailwind v4 static project - Nav: sticky header with logo, section links, waitlist CTA - Hero: headline, subheadline, dual CTA, inbox preview mockup - Features: four-step loop cards (Monitor/Curate/Synthesize/Publish) - Pricing: three-tier table (Free / Team €29 / Enterprise) - Social proof: three placeholder testimonials - Waitlist: form UI with consent checkbox (service integration TBD) - SEO: title, description, Open Graph, Twitter Card, canonical URL - Responsive: mobile-first layout across all sections - Update root .gitignore to exclude landing/node_modules, dist, .astro - Add CI Landing job (npm ci + build + audit) - Add make run-landing, landing-install, landing-build targets Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add a typed translations file (translations.ts) covering all landing page sections in English and French. Configure Astro built-in i18n routing (prefixDefaultLocale: false) so EN stays at / and FR lives at /fr/. Each component now receives a t: Translations prop; a locale switcher in the Nav links between the two versions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
landing//= EN,/fr/= FR)translations.tscovering all sections: nav, hero, features,pricing, social proof, waitlist, footer
<html lang="">set dynamically per locale viaBaseLayoutWhy
Phase 2 of the roadmap — a public marketing + waitlist page for
Signalist before the app launches.
How
astro.config.mjs:i18n.prefixDefaultLocale: falseso EN stays at/and FR at/fr/src/i18n/translations.ts:as constobject for both locales,exports
Translations(union type) andLocalet: Translationsprop; icons/colors stay aspresentation constants in each component
src/pages/index.astro+src/pages/fr/index.astroimport thematching locale and pass
tto every componentVerification
npm run build— 2 pages built cleanly (/index.html,/fr/index.html)landingjob:npm ci && npm run build && npm audit --audit-level=highFollow-up
🤖 Generated with Claude Code